Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1064

reference
881-tree-1
name
1064
tree-preservation-order

undefined

881-tpo-1
uprn
address-text
point
POINT (-1.020192 50.879742)
geometry
MULTIPOLYGON (((-1.020135 50.879735,-1.020137 50.879747,-1.020145 50.879757,-1.020158 50.879765,-1.020173 50.879770,-1.020191 50.879772,-1.020209 50.879770,-1.020225 50.879765,-1.020237 50.879757,-1.020246 50.879748,-1.020249 50.879736,-1.020246 50.879725,-1.020238 50.879715,-1.020226 50.879707,-1.020210 50.879702,-1.020192 50.879700,-1.020175 50.879702,-1.020159 50.879707,-1.020146 50.879714,-1.020138 50.879724,-1.020135 50.879735)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL